Interface display for infusion module

ABSTRACT

A method including receiving, in a main frame of a patient care unit, an infusion information from a medication delivery module coupled with the main frame is provided. The medication delivery module being mounted on a plug-in port associated with the main frame. The method also includes displaying, on a display in the main frame, an individual channel card including at least a portion of the infusion information from the medication delivery module and orienting an edge of the individual channel card toward a location of the plug-in port relative to the main frame, the edge having a visual indicator that visually indicates an orientation of the module associated with the individual channel card. The method also includes expanding the individual channel card to display a detailed portion of the infusion information upon receipt of a user selection. A system and a non-transitory, computer readable medium including instructions to perform the above method are also provided.

TECHNICAL FIELD

The present disclosure is generally related to a patient care unit (PCU)configured for medication delivery. More specifically, the presentdisclosure relates to methods and systems to display infusioninformation in expandable patient care units having multiple medicationdelivery modules.

BACKGROUND

Patient care units such as infusion medication devices may includemodular platforms that are expandable with multiple medication deliverymodules to handle more than one type of medication delivery to apatient. As the infusion module is expanded, typically each individualinfusion type device in the module provides its own user display andinterface. This may result in a wide variety of display types that mayconfuse or distract the user during infusion and other medicationdelivery procedures. Further, alert notifications when one or more ofthe medication delivery modules in the patient care unit is notperforming appropriately may be lost or hard to notice for a user.

SUMMARY

In a first embodiment, a computer-implemented method includes receiving,in a main frame of a patient care unit, infusion information from afirst medication delivery module electronically coupled to the mainframe via a first plug-in port associated with the main frame;displaying, on a display of the main frame, a first graphical channelcard comprising at least a portion of the infusion information receivedfrom the first medication delivery module, the first graphical channelcard having a first visual indicator along an edge of the firstgraphical channel card; dynamically orienting the edge of the firstgraphical channel card and the first visual indicator toward a location,relative to the main frame, of the first plug-in port and the firstmedication delivery module; receiving a user selection at the mainframe; and expanding the first graphical channel card to display adetailed portion of the infusion information upon receipt of a userselection. Other aspects include corresponding systems, apparatus, andcomputer program products for implementation of the method.

In some embodiments a system includes a memory storing instructions andone or more processors coupled with the memory and configured to executethe instructions to cause the system to receive, in a main frame of apatient care unit, a first infusion information from a first medicationdelivery module electronically coupled with the main frame via a firstplug-in port associated with the main frame; display, in the main frame,a first graphical channel card comprising at least a portion of thefirst infusion information from the first medication delivery module,the first graphical channel card having a first visual indicator alongan edge of the first graphical channel card; dynamically orient thefirst graphical channel card toward a location of the first plug-in portrelative to the main frame; determine that a second medication deliverymodule was electronically coupled to the main frame via a second plug-inport associated with the main frame on a side of the main frame oppositeto the first plug-in port; receive a second infusion information fromthe second medication delivery module; and dynamically display thesecond infusion information in a second graphical channel card on thedisplay of the main frame, adjacent to the first graphical channel card,with a visual indicator of the second graphical channel card orientedtoward the second medication delivery module. Other aspects includecorresponding methods, apparatus, and computer program products forimplementation of the system.

In further embodiments, a non-transitory, computer-readable mediumstores instructions which, when executed by a processor in a computer,cause the computer to perform a method. The method includes receiving,in a main frame of a patient care unit, an infusion information from afirst medication delivery module electronically coupled with the mainframe via a first plug-in port associated with the main frame;displaying, on a display of the main frame, a first graphical channelcard comprising at least a portion of the infusion information receivedfrom the first medication delivery module, the first graphical channelcard having a first visual indicator along an edge of the firstgraphical channel card; orienting the first graphical channel cardtoward a location of the first plug-in port relative to the main frameso that the edge and the first visual indicator are oriented towards aside of the main frame corresponding to the first plug-in port; andexpanding the first graphical channel card, from a first summary stateto a second detail state, to display a detailed portion of the infusioninformation upon receipt of a user selection. Other aspects includecorresponding systems, apparatus, methods, and computer program productsfor implementation of the computer-readable medium.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a medication delivery system including a patient careunit and a controller, according to some embodiments.

FIG. 2 illustrates a patient care unit expanded with medication deliverymodules, according to some embodiments.

FIG. 3 illustrates a patient care unit including a main displaymirroring individual module screens, according to some embodiments.

FIG. 4 illustrates a medication delivery data structure shared between amedication delivery module, a patient care unit, and a controller,according to some embodiments.

FIG. 5 illustrates a flowchart in a method for displaying a medicationdelivery information, according to some embodiments.

FIGS. 6A-6G illustrates example channel cards that may be expanded andcontracted according to various implementations.

FIG. 7 is a block diagram illustrating an example computer system withwhich the client and server of FIGS. 1 and 2, and the method of FIG. 5can be implemented, according to some embodiments.

In the figures, elements having the same or similar reference numeralhave the same or similar functionality or configuration, unlessexpressly stated otherwise.

DETAILED DESCRIPTION

Embodiments as disclosed herein include PCUs that are configured to beexpanded with multiple medication delivery modules to handle delivery ofmore than one type of medication to a patient. The PCU includes a mainframe having a main display that displays medication deliveryinformation received from each of the individual medication deliverymodules. Accordingly, embodiments as disclosed herein provide a uniformdisplay type for the different medication delivery units, to avoid userconfusion or distraction. Also, by providing a uniform data displayacross multiple types of medication delivery modules, embodiments asdisclosed herein facilitate a user verification and validation, reducingthe time a user needs to confirm or adjust any of the medicationdelivery settings (e.g., in case of an emergency). In some embodimentsan alert notification may be displayed prominently in a main frame ofthe PCU, when one or more of the medication delivery modules is notperforming appropriately.

Some of the advantages of embodiments consistent with the presentdisclosure include an improved safety in medication delivery protocols.Embodiments as disclosed herein are suitable for emergency situationswhen a rapid action is desirable, e.g., when a medication deliverymodule stops working, or continues to deliver medication when it shouldstop, provides the wrong medication, the wrong dose, or at the wrongrate. Some of the emergency situations may include determining that acertain fluid or medication container will be emptied before the totaldose is delivered to the patient. Accordingly, a quick action by a nurseor other personnel may resolve the emergency before it becomes a moreserious problem.

FIG. 1 illustrates a medication delivery system 10 including a patientcare unit (PCU) 100 and a controller 110, according to some embodiments.Medication delivery system 10 may include a frame 140 supporting acontainer 143 having a fluid 170.

In some embodiments, medication delivery system 10 is an intravenousdelivery system and fluid 170 may include an intravenous fluid to beadministered to patient 160 through a blood vessel. Accordingly, fluid170 may include blood, plasma, or a medication. Fluid 170 may be anyliquid suitable for intravenous delivery. Common intravenous liquidsinclude crystalloids (e.g., saline, Lactated Ringers, glucose,dextrose), colloids (e.g., hydroxyethyl starch, gelatin), liquidmedications, buffer solutions, and blood products (e.g., packed redblood cells, plasma, clotting factors) or blood substitutes (e.g.,artificial blood) that are desired to be injected intravenously to apatient 160. A fluid line 130 carries fluid 170 from container 143 topatient 160. In some embodiments, PCU 100 includes a pump 145 to movefluid 170 through fluid line 130.

Medication delivery system 10 includes a PCU 100 mechanically coupledwith fluid line 130. In some embodiments, PCU 100 is configured toprovide multiple measurements of the fluid flow. In some embodiments,PCU 100 is configured to measure fluid pressure, fluid flow rate, andthe like. PCU 100 may include a memory 151 storing instructions which,when executed by a processor 152, cause PCU 100 to perform, at leastpartially, steps in methods as disclosed herein.

In some embodiments, the operation of PCU 100 may be controlledwirelessly by a remote controller 110 located, for example, at a nursestation. The wireless communication may be performed by an antenna 175on the controller side and an antenna 155 on frame 140. Controller 110includes a processor 112 and a memory 120. Memory 120 may includecommands and instructions, which when executed by processor 112, causecontroller 110 to perform at least partially some of the steps includedin methods consistent with the present disclosure. Furthermore, PCU 100may wirelessly communicate with controller 110 via antenna 155, toreceive instructions from and provide data to, controller 110. In someembodiments, PCU 100 is configured to provide a visual status (e.g., aprogress report) of the medication delivery (e.g., for a nurse or othermedication personnel), and to transmit the visual status and othermedication delivery information to controller 110.

Memory 120 in controller 110 stores clinical information related to themedication delivery. Accordingly, controller 110 provides PCU 100 atleast the dynamic part of the clinical information, including the totalamount of medication to be delivered, at what rate, at what time tostart delivery, and at what time to stop, or pause, the medicationdelivery. PCU 100 provides, to controller 110, a status of how far ithas progressed to a certain delivery goal. Further, in some embodimentsPCU 100 stores at least a portion of the clinical information, and astatus of the medication delivery in memory 151.

In some embodiments, a second controller 110 may take over control ofPCU 100 (e.g., when a patient is transferred from one room or unit toanother and a first controller stays in the room while a secondcontroller moves with the patient).

Controller 110, and PCU 100 may communicate through antennas 155 and 175via a Bluetooth, Wi-Fi, or any other radio-frequency protocol.Accordingly, controller 110 may be configured to process data from PCU100 and store a medication delivery progress update in memory 120. Insome embodiments, other characteristics of the fluid relevant for amedication delivery or infusion may be stored by controller 110 inmemory 120. A valve 190 in fluid line 130 may be operated to allow fluid170 to flow into patient 160 when PCU 100 detects a bubble content lowerthan a predetermined threshold. In some embodiments, valve 190 may beclosed by a motor in PCU 100 (e.g., an occlusion is detected in fluidline 130, or a bubble level is above a pre-selected threshold).

Furthermore, controller 110 may provide an alarm to a centralized systemwhen a bubble count in PCU 100 becomes higher than a threshold. In someembodiments, controller 110 may also provide commands to regulate thetemperature of fluid 170 (e.g., via a thermostat) based on a bubblecount or a temperature measurement provided by PCU 100.

FIG. 2 illustrates a PCU 200 including a main frame 201 expanded withmedication delivery modules 220-1 and 220-2 (hereinafter, collectivelyreferred to as “medication delivery modules 220”), according to someembodiments. In some embodiments, medication delivery modules 220include plug-in ports 231 and 235 for expansion. Accordingly, a newmedication delivery module may be attached to PCU 200 by coupling aconnector through plug-in ports 231 and 235. Plug-in port 235 mayinclude electrical terminals so that the added medication deliverymodule 220 may transmit and receive information to and from a main frame201. In some embodiments, the added medication delivery module 220 mayalso receive power from main frame 201 through the plug-in port 235.Main frame 201 may include a main display 210, a memory 251 and aprocessor 252 (e.g., memory 151 and processor 152). Module displays211-1 and 211-2 (hereinafter, collectively referred to as “moduledisplays 211”) may be configured to display medication delivery statusand further information associated with each of medication deliverymodules 220.

Main display 210 is configured to display individual channel cards 213-1and 213-2 (hereinafter, collectively referred to as “graphic channelcards” or “individual channel cards 213”). Each individual channel card213 graphically displays information received from a respective one ofmedication modules 220, including information also displayed on acorresponding module displays 211. In some embodiments, main frame 201includes a communications module 218 and an antenna 255, configured tocommunicate wirelessly with a controller (e.g., controller 110), or witha network.

FIG. 3 illustrates a PCU 300 including a main frame 301 having a maindisplay 310 that mirrors individual module displays, 311-1, 311-2 and311-3 (hereinafter, collectively referred to as “module displays 311”),according to some embodiments. Main frame 301 includes a memory 351storing instructions and a processor 352 configured to execute theinstructions to cause main frame 301 to perform at least partially someof the steps in methods as disclosed herein. In some embodiments, mainframe 301 also includes a communications module 318 and an antenna 355,configured to communicate wirelessly with a controller (e.g., controller110), or with a network.

Main frame 301 is expanded with a medication delivery module 320-1 thatis configured to deliver a fluid 370-1, a medication delivery module320-2, and a medication delivery module 320-3 configured to deliver afluid 370-2. Medication delivery modules 320-1, 320-2 and 320-3 will becollectively referred to, hereinafter, as “medication delivery modules320.” Module displays 311 may be configured to display medicationdelivery status and further information associated with each ofmedication delivery modules 320.

Similarly to main display 210 in PCU 200, main display 310 includesindividual channel cards 313-1, 313-2, and 313-3 (hereinafter,collectively referred to as “individual channel cards 313”). Individualchannel cards 313 include graphically displayed information from each ofmodule displays 311. In some embodiments, individual channel cards 313may include visual indicators 323-1, 323-2, and 323-3, respectively(hereinafter, collectively referred to as “visual indicators 323”) whichmay specify the orientation of the channel card. In variousimplementations, visual indicators 323 are graphics along an edge of achannel card. By virtue of which edge of the channel card a visualindicator is displayed, the visual indicator visually associates to auser the location of the corresponding medication delivery module. Forexample, visual indicator 323-1 is placed on the left side ofidentification card 313-1, indicating that medication delivery module320-1 is plugged-in to the left of main frame 301. Likewise, visualindicator 323-2 is placed on the right side of identification card313-2, indicating that medication delivery module 320-2 is plugged-in tothe right of main frame 301. And visual indicator 323-3 is placed on theright side of identification card 313-3, indicating that medicationdelivery module 320-3 is plugged-in to the right of main frame 301.

In some embodiments, visual indicators 323 may include a distinct colorbanner to indicate a status of each of medication delivery modules 320associated with them. For example, visual indicator 323-1 may include agreen banner, indicating that medication delivery module 320-1 is activeand working properly. Visual indicator 323-2 includes an orange banner,indicating that medication delivery module 320-2 may be paused,inactive, or may have an error condition. Visual indicator 323-3includes a green banner, indicating that medication delivery module320-3 is active and working properly. Other color codes may be used,e.g., a red banner may indicate a medication delivery module that has analarm flag. In some embodiments, respective visual indicator 323 of anidentification card 313 may also be configured to display a graphicindicating the amount of fluid that is being infused by a module 320associated with the identification card 313. For example, visualindicator 323 may include a graphic of a fluid drop 373, or an animationof a fluid dripping (e.g., within the banner, along the edge).

In some embodiments, one of medication delivery modules 320 may beremoved from PCU 300 to be installed or plugged-in to a second PCU.Accordingly, in some embodiments the infusion information in thecorresponding module display 311 may still be displayed while themedication delivery module 320 is unplugged.

A first medication delivery module may be electronically coupled to amain frame via a first plug-in port associated with the main frame. Inthis regard, the plug-in port may be a plug-in port directly on a firstside of the main frame, so that the module plugs directly into theplug-in port when it is mounted to the main frame (e.g., to receivemodule 311-2 in FIG. 3). Or, the plug-in port may be a plug-in port on aside of another module such that the first medication delivery module iselectronically coupled to the main frame via the other module (e.g., toreceive module 311-3 in FIG. 3). As medication delivery modules areinstalled, new graphic channel cards are displayed on the display of themain frame, each orientated toward a newly-installed module. The mainframe may receive an indication that a second medication delivery modulewas electronically coupled to the main frame via a second plug-in portassociated with the main frame at a side of the main frame opposite thefirst plug-in port and the first medication delivery module. The mainframe may then dynamically display, on the display screen of the mainframe in response to receiving the indication, a second graphicalchannel card including at least a portion of a second infusioninformation. The second graphical channel card is displayed orientedtoward the second plug-in port and the second medication delivery moduleand opposite to a side of the main frame where the first medicationdelivery module is electronically coupled via the first plug-in port. Asdepicted in FIG. 3, the graphical channel cards are displayed adjacentto each other as they are newly-displayed on display 310.

FIG. 4 illustrates a display of an infusion information 400 sharedbetween a medication delivery module (e.g., medication delivery modules220 and 320), a PCU (e.g., PCUs 100, 200 and 300), and a controller(e.g., controller 110), according to some embodiments. Infusioninformation 400 provides updated information about the settings of themedication delivery module, and a status of a medication delivery.According to various embodiments, infusion information 400 may begraphically displayed on a display screen, as shown in any of individualchannel cards 213, or 313.

In some embodiments, infusion information 400 includes a patientidentification (ID) 402, and a nurse ID 404. A medication name label(“Drug”) 412 indicates the name of the drug configured for delivery topatient 402, under the care of nurse 404. According to variousembodiments, infusion information 400 may include information pertainingto a fluid that is being infused by a module 320 (e.g., an amount,bolus, rate of infusion, etc.). When displayed, infusion information 400may include a dosage indicator 414, a delivery rate indicator 416, and astatus indicator 418. Status indicator 418 may indicate the amount ofdrug delivered to the patient.

FIG. 5 illustrates a flowchart in a method 500 for displaying amedication delivery information, according to some embodiments. Method500 may be performed at least partially by a PCU (e.g., PCUs 100, 200and 300), while communicating with a controller (e.g., controller 110).At least some of the steps in method 500 may be performed by a computerhaving a processor executing commands stored in a memory of the computer(e.g., processors 112, 152, 252 and 352, and memories 120, 151, 251 and351). In some embodiments, steps as disclosed in method 500 may includeretrieving, editing, and/or storing files in a database that is part of,or is communicably coupled to, a memory (e.g., memories 251 and 351). Insome embodiments, information transmitted between one or more devices ina system performing method 500 may include an infusion information(e.g., fluid infusion information 400). Methods consistent with thepresent disclosure may include at least some, but not all, of the stepsillustrated in method 500, performed in a different sequence.Furthermore, methods consistent with the present disclosure may includeat least two or more steps as in method 500 performed overlapping intime, or almost simultaneously.

Step 502 includes identifying a device docked on a plug-in port in apatient care unit. In some embodiments, step 502 includes verifying thatthe device is associated with a patient registered with a PCU associatedwith the module display.

Step 504 includes receiving, in the main frame of the patient care unit(e.g., main frames 201 or 301), an infusion information from themedication delivery module coupled with the main frame (e.g., medicationdelivery modules 220 or 320), the medication delivery module beingmounted on a plug-in port associated with the main frame (e.g., plug-inports 231 and 235). In some embodiments, the main frame comprises amemory circuit (e.g., memories 251 and 351), and step 504 includesstoring the infusion information in the memory circuit.

Step 506 includes displaying, in the main frame, an individual channelcard including at least a portion of the infusion information from themedication delivery module. In some embodiments, step 506 includesmirroring a display in the medication delivery module (e.g., displays210 and 310). In some embodiments, step 506 includes providing a displayinformation to a display in the medication delivery module. In someembodiments, step 506 includes displaying a fluid drop, or an animationof a dripping fluid when the medication delivery module is delivering aninfusion. In some embodiments, step 506 includes displaying a secondindividual channel card including at least a portion of a secondinfusion information from a second medication delivery module coupledwith the main frame. In some embodiments, step 506 includes providing avisual indicator in the individual channel card, the visual indicatorcomprising a color banner on a side of the individual channel card, thecolor banner consistent with a status of the medication delivery module,or an icon of a fluid drop (e.g., fluid drop 373), indicating activeinfusion.

Step 508 includes orienting the individual channel card toward alocation of the plug-in port relative to the main frame. For example, insome embodiments, when there is a medication delivery module on eitherside of the main frame, two individual channel cards may be displayed inthe main frame and step 508 may include orienting each of the twoindividual channel cards in opposite directions. Further, in someembodiments, step 508 may include changing the orientation of theindividual channel card when the associated medication delivery moduleis switched from a plug-in port on one side of the main frame to aplug-in port on the other side of the main frame.

In yet some implementations, a step 508 may include a user moving theassociated medication delivery module from one side of the main frame tothe opposite side of the main frame, and obtaining the infusioninformation from the individual channel card associated with themedication delivery module and which has switched orientation toindicate the position change of the associated medication deliverymodule. In this regard, the main frame receives an indication that thefirst medication delivery module was electronically decoupled from afirst plug-in port and then electronically coupled to the main frame viaa second plug-in port associated with the main frame on a side of themain frame opposite the first plug-in port. The main frame thenredisplays the channel card for the first medication delivery module anddynamically orients the edge of the channel card and the first visualindicator toward the second plug-in port.

Step 510 includes expanding the individual channel card to display adetailed portion of the infusion information upon receipt of a userselection. An individual channel card may be expanded or contracteddynamically (e.g., automatically) based on a number of active channelsin the patient care unit, and/or a number of individual channel cardsdisplayed on the same display screen. As described further with respectto FIG. 6A-6G, when expanded, an individual channel card may provide amore descriptive or detailed set of information regarding an infusion orparameters pertaining to the infusion.

In some embodiments, the module display comprises a touchscreen display,and step 510 includes receiving reprogramming commands for the deviceusing the individual channel card in the touchscreen display. In someembodiments, the module display comprises a touchscreen display and step510 includes detecting a touch by a user on the touchscreen display ofthe individual channel card. In some embodiments, step 510 includesissuing an alarm to a central server when the device docked on theplug-in port is not recognized by a PCU associated with the moduledisplay. In some embodiments, step 510 includes indicating, with thevisual indicator, a state of the device docked on the plug-in port,wherein the state of the device comprises at least one of an error stateand a running state. In some embodiments, step 510 includes adjusting afont size for the individual channel card to enhance a viewerperspective. In some embodiments, step 510 includes verifying that themedication delivery module is associated with a patient registered withthe patient care unit. In some embodiments, the main frame comprises acommunications module, and step 510 includes transmitting to acontroller, via the communications module, the infusion information.

FIGS. 6A-6G are illustrations of example channel cards that may beexpanded and contracted according to various implementations of thesubject technology. FIG. 6A is an example of four channel cards beingdisplayed on a main display (e.g., main display 310) for four respectiveindividual channel cards (e.g., individual channel cards 313)corresponding to module displays (e.g., module displays 311). Channelcards A and B are aligned with their indicators to the left to representmedication delivery modules (e.g., medication delivery modules 320)attached to the left-hand side of main frame 301, and channel cards Cand D are aligned with their indicators to the right to representmedication delivery modules attached to the right-hand side of the mainframe (e.g., main frame 301).

Each channel card may be initially displayed without information. Onselecting a channel card (e.g., channel card 613-1 A, 613-2 B, 623-1 C,or 623-2 D), the main display is updated to expand the channel card toan information screen (e.g., FIG. 6B) into which infusion parameters maybe entered for storage in memory (e.g., in memory 120), for utilizationin an infusion. FIG. 6C is an example of channel card A having beenexpanded to display descriptive or detailed set of information regardingan infusion or parameters pertaining to the infusion. Once theinformation has been entered, the card may be updated graphically, asshown by FIG. 6D, to display the information stored in memory, andparameters of an ongoing infusion. In the depicted example, FIG. 6Ddisplays channel card A as displaying information for an activelyprogrammed infusion operation programmed for a corresponding medicationdelivery module 320, while channel cards 613-2, 623-1 and 623-2 (B-D)are displayed without this information, indicating that thecorresponding medication delivery modules have yet to be programmed.

FIG. 6E is an example of a channel card displaying information for aninfusion operation of a corresponding medication delivery module. Onselection of the channel card, the main display is updated as shown inFIG. 6F to display the channel card in an expanded state, withprogramming information displayed. The information displayed may includegraphical or virtual buttons for activating and ending an infusionoperation. FIG. 6G is an example of the channel card A returning to itspreprogrammed state (e.g., no longer displaying infusion information400) after the infusion operation is ended by virtual button input. Insome aspects, a confirmation screen may be displayed requesting furtherconfirmatory input from a user before a parameter is committed to aninfusion operation or stored, or an active infusion operation isinitiated or ended.

FIG. 7 is a block diagram illustrating an example computer system 700with which the client and server of FIGS. 1 and 2, and the method ofFIG. 5 can be implemented, according to some embodiments. Computersystem 700 (e.g., main frame 301) includes a bus 708 or othercommunication mechanism for communicating information, and a processor702 (e.g., processors 152, 252 and 352) coupled with bus 708 forprocessing information. By way of example, the computer system 700 maybe implemented with one or more processors 702. Processor 702 may be ageneral-purpose microprocessor, a microcontroller, a Digital SignalProcessor (DSP), an Application Specific Integrated Circuit (ASIC), aField Programmable Gate Array (FPGA), a Programmable Logic Device (PLD),a controller, a state machine, gated logic, discrete hardwarecomponents, or any other suitable entity that can perform calculationsor other manipulations of information.

Computer system 700 can include, in addition to hardware, a code thatcreates an execution environment for the computer program in question,e.g., code that constitutes processor firmware, a protocol stack, adatabase management system, an operating system, or a combination of oneor more of them stored in an included memory 704 (e.g., memories 151,251 and 351), such as a Random Access Memory (RAM), a flash memory, aRead Only Memory (ROM), a Programmable Read-Only Memory (PROM), anErasable PROM (EPROM), registers, a hard disk, a removable disk, aCD-ROM, a DVD, or any other suitable storage device, coupled to bus 708for storing information and instructions to be executed by processor702. The processor 702 and the memory 704 can be supplemented by, orincorporated in, a special purpose logic circuitry.

The instructions may be stored in the memory 704 and implemented in oneor more computer program products, i.e., one or more modules of computerprogram instructions encoded on a computer readable medium for executionby, or to control the operation of, the computer system 700, andaccording to any method well known to those skilled in the art,including, but not limited to, computer languages such as data-orientedlanguages (e.g., SQL, dBase), system languages (e.g., C, Objective-C,C++, Assembly), architectural languages (e.g., Java, .NET), andapplication languages (e.g., PHP, Ruby, Perl, Python). Instructions mayalso be implemented in computer languages such as array languages,aspect-oriented languages, assembly languages, authoring languages,command line interface languages, compiled languages, concurrentlanguages, curly-bracket languages, dataflow languages, data-structuredlanguages, declarative languages, esoteric languages, extensionlanguages, fourth-generation languages, functional languages,interactive mode languages, interpreted languages, iterative languages,list-based languages, little languages, logic-based languages, machinelanguages, macro languages, metaprogramming languages, multiparadigmlanguages, numerical analysis, non-English-based languages,object-oriented class-based languages, object-oriented prototype-basedlanguages, off-side rule languages, procedural languages, reflectivelanguages, rule-based languages, scripting languages, stack-basedlanguages, synchronous languages, syntax handling languages, visuallanguages, wirth languages, and xml-based languages. Memory 704 may alsobe used for storing temporary variable or other intermediate informationduring execution of instructions to be executed by processor 702.

A computer program as discussed herein does not necessarily correspondto a file in a file system. A program can be stored in a portion of afile that holds other programs or data (e.g., one or more scripts storedin a markup language document), in a single file dedicated to theprogram in question, or in multiple coordinated files (e.g., files thatstore one or more modules, subprograms, or portions of code). A computerprogram can be deployed to be executed on one computer or on multiplecomputers that are located at one site or distributed across multiplesites and interconnected by a communication network. The processes andlogic flows described in this specification can be performed by one ormore programmable processors executing one or more computer programs toperform functions by operating on input data and generating output.

Computer system 700 further includes a data storage device 706 such as amagnetic disk or optical disk, coupled to bus 708 for storinginformation and instructions. Computer system 700 may be coupled viainput/output module 710 to various devices. Input/output module 610 canbe any input/output module. Exemplary input/output modules 710 includedata ports such as USB ports. The input/output module 710 is configuredto connect to a communications module 712. Exemplary communicationsmodules 712 (e.g., communications modules 218 and 318) includenetworking interface cards, such as Ethernet cards and modems. Incertain aspects, input/output module 710 is configured to connect to aplurality of devices, such as an input device 714 (e.g., main display310) and/or an output device 716 (e.g., main display 310). Exemplaryinput devices 714 include a keyboard and a pointing device, e.g., amouse or a trackball, by which a user can provide input to the computersystem 700. Other kinds of input devices 714 can be used to provide forinteraction with a user as well, such as a tactile input device, visualinput device, audio input device, or brain-computer interface device.For example, feedback provided to the user can be any form of sensoryfeedback, e.g., visual feedback, auditory feedback, or tactile feedback;and input from the user can be received in any form, including acoustic,speech, tactile, or brain wave input. Exemplary output devices 716include display devices, such as a LCD (liquid crystal display) monitor,for displaying information to the user.

According to one aspect of the present disclosure, PCU 100 andcontroller 110 can be implemented using a computer system 700 inresponse to processor 702 executing one or more sequences of one or moreinstructions contained in memory 704. Such instructions may be read intomemory 704 from another machine-readable medium, such as data storagedevice 706. Execution of the sequences of instructions contained in mainmemory 704 causes processor 702 to perform the process steps describedherein. One or more processors in a multi-processing arrangement mayalso be employed to execute the sequences of instructions contained inmemory 704. In alternative aspects, hard-wired circuitry may be used inplace of or in combination with software instructions to implementvarious aspects of the present disclosure. Thus, aspects of the presentdisclosure are not limited to any specific combination of hardwarecircuitry and software.

Various aspects of the subject matter described in this specificationcan be implemented in a computing system that includes a back-endcomponent, e.g., as a data server, or that includes a middlewarecomponent, e.g., an application server, or that includes a front-endcomponent, e.g., a client computer having a graphical user interface ora Web browser through which a user can interact with an implementationof the subject matter described in this specification, or anycombination of one or more such back-end, middleware, or front-endcomponents. The components of the system can be interconnected by anyform or medium of digital data communication, e.g., a communicationnetwork. The communication network can include, for example, any one ormore of a LAN, a WAN, the Internet, and the like. Further, thecommunication network can include, but is not limited to, for example,any one or more of the following network topologies, including a busnetwork, a star network, a ring network, a mesh network, a star-busnetwork, tree or hierarchical network, or the like. The communicationsmodules can be, for example, modems or Ethernet cards.

Computer system 700 can include clients and servers. A client and serverare generally remote from each other and typically interact through acommunication network. The relationship of client and server arises byvirtue of computer programs running on the respective computers andhaving a client-server relationship with each other. Computer system 700can be, for example, and without limitation, a desktop computer, laptopcomputer, or tablet computer. Computer system 700 can also be embeddedin another device, for example, and without limitation, a mobiletelephone, a PDA, a mobile audio player, a Global Positioning System(GPS) receiver, a video game console, and/or a television set top box.

The term “machine-readable storage medium” or “computer readable medium”as used herein refers to any medium or media that participates inproviding instructions to processor 702 for execution. Such a medium maytake many forms, including, but not limited to, non-volatile media,volatile media, and transmission media. Non-volatile media include, forexample, optical or magnetic disks, such as data storage device 706.Volatile media include dynamic memory, such as memory 704. Transmissionmedia include coaxial cables, copper wire, and fiber optics, includingthe wires that include bus 708. Common forms of machine-readable mediainclude, for example, floppy disk, flexible disk, hard disk, magnetictape, any other magnetic medium, CD-ROM, DVD, any other optical medium,punch cards, paper tape, any other physical medium with patterns ofholes, a RAM, a PROM, an EPROM, a FLASH EPROM, any other memory chip orcartridge, or any other medium from which a computer can read. Themachine-readable storage medium can be a machine-readable storagedevice, a machine-readable storage substrate, a memory device, acomposition of matter affecting a machine-readable propagated signal, ora combination of one or more of them.

The foregoing description is provided to enable a person skilled in theart to practice the various configurations described herein. While thesubject technology has been particularly described with reference to thevarious figures and configurations, it should be understood that theseare for illustration purposes only and should not be taken as limitingthe scope of the subject technology.

There may be many other ways to implement the subject technology.Various functions and elements described herein may be partitioneddifferently from those shown without departing from the scope of thesubject technology. Various modifications to these configurations willbe readily apparent to those skilled in the art, and generic principlesdefined herein may be applied to other configurations. Thus, manychanges and modifications may be made to the subject technology, by onehaving ordinary skill in the art, without departing from the scope ofthe subject technology.

As used herein, the phrase “at least one of” preceding a series ofitems, with the term “and” or “or” to separate any of the items,modifies the list as a whole, rather than each member of the list (e.g.,each item). The phrase “at least one of” does not require selection ofat least one of each item listed; rather, the phrase allows a meaningthat includes at least one of any one of the items, and/or at least oneof any combination of the items, and/or at least one of each of theitems. By way of example, the phrases “at least one of A, B, and C” or“at least one of A, B, or C” each refer to only A, only B, or only C;any combination of A, B, and C; and/or at least one of each of A, B, andC.

Furthermore, to the extent that the term “include,” “have,” or the likeis used in the description or the claims, such term is intended to beinclusive in a manner similar to the term “comprise” as “comprise” isinterpreted when employed as a transitional word in a claim. The word“exemplary” is used herein to mean “serving as an example, instance, orillustration.” Any embodiment described herein as “exemplary” is notnecessarily to be construed as preferred or advantageous over otherembodiments.

A reference to an element in the singular is not intended to mean “oneand only one” unless specifically stated, but rather “one or more.” Theterm “some” refers to one or more. All structural and functionalequivalents to the elements of the various configurations describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and intended to be encompassed by the subject technology.Moreover, nothing disclosed herein is intended to be dedicated to thepublic regardless of whether such disclosure is explicitly recited inthe above description.

While certain aspects and embodiments of the subject technology havebeen described, these have been presented by way of example only, andare not intended to limit the scope of the subject technology. Indeed,the novel methods and systems described herein may be embodied in avariety of other forms without departing from the spirit thereof. Theaccompanying claims and their equivalents are intended to cover suchforms or modifications as would fall within the scope and spirit of thesubject technology.

What is claimed is:
 1. A computer-implemented method, comprising:receiving, in a main frame of a patient care unit, a first indicationthat a first medication delivery module was electronically coupled tothe main frame via a first plug-in port of the main frame; displaying,on a display of the main frame responsive to receiving the firstindication, a first graphical channel card representative of the firstmedication delivery module and having a first visual indicator along anedge of the first graphical channel card, wherein the first visualindicator is configured to display information associated with a statusof the first medication delivery module; dynamically orienting,responsive to receiving the first indication, the edge of the firstgraphical channel card and the first visual indicator in a directiontoward the first plug-in port coupling the main frame to the firstmedication delivery module; receiving infusion information from thefirst medication delivery module via the first plug-in port; displaying,on the display of the main frame, within the first graphical channelcard, at least a portion of the received infusion information; receivinga user selection at the main frame; and expanding the first graphicalchannel card to display a detailed portion of the infusion informationupon receipt of a user selection.
 2. The computer-implemented method ofclaim 1, wherein displaying the first graphical channel card on thedisplay of the main frame comprises mirroring a display of the at leastthe portion of the infusion information at the first medication deliverymodule.
 3. The computer-implemented method of claim 2, wherein displayinformation is provided from the main frame to a display of the firstmedication delivery module to facilitate the display at the firstmedication delivery module.
 4. The computer-implemented method of claim1, wherein the first visual indicator comprises a graphical strip alongthe edge of the first graphical channel card, and displaying informationassociated with the status comprises displaying an indication of a fluidflow in the first visual indicator of the first graphical channel cardwhen the first medication delivery module is delivering an infusion. 5.The computer-implemented method of claim 1, further comprising:receiving a second indication that the first medication delivery modulewas electronically decoupled from the first plug-in port and thenelectronically coupled to the main frame via a second plug-in port ofthe main frame on a side of the main frame opposite the first plug-inport; and dynamically reorienting, responsive to receiving the secondindication, the edge of the first graphical channel card and the firstvisual indicator toward the second plug-in port.
 6. Thecomputer-implemented method of claim 1, further comprising: receiving asecond indication that a second medication delivery module waselectronically coupled to the main frame via a second plug-in port ofthe main frame at a side of the main frame opposite the first plug-inport and the first medication delivery module; and dynamicallydisplaying, with the first graphical channel card, on the display of themain frame in response to receiving the second indication, a secondgraphical channel card oriented toward the second plug-in port and suchthat an edge of the second graphical channel card is oriented in adirection opposite the edge of the first graphical channel card.
 7. Thecomputer-implemented method of claim 1, wherein the first visualindicator comprises a color banner on a side of the first graphicalchannel card, a color of the color banner being dynamically selectedbased on the status of the first medication delivery module.
 8. Thecomputer-implemented method of claim 1, wherein expanding the firstgraphical channel card to display a detailed portion of the infusioninformation comprises adjusting a font size for the first graphicalchannel card to enhance a viewer perspective.
 9. Thecomputer-implemented method of claim 1, further comprising: verifying,by the main frame, that the first medication delivery module isassociated with a patient registered with the patient care unit.
 10. Thecomputer-implemented method of claim 1, wherein the main frame comprisesa communications module, the computer-implemented method furthercomprising transmitting to a controller, via the communications module,the infusion information.
 11. A system, comprising: a memory storinginstructions; and one or more processors coupled with the memory andconfigured to execute the instructions to cause the system to: receive,in a main frame of a patient care unit, an indication that a firstmedication delivery module was electronically coupled with the mainframe via a first plug-in port of the main frame; provide for display ona display device of the main frame, responsive to receiving theindication, a first graphical channel card representative of the firstmedication delivery module and having a first visual indicator along anedge of the first graphical channel card, wherein the first visualindicator is configured to display information associated with a statusof the first medication delivery module; dynamically orient, responsiveto receiving the indication, the edge of the first graphical channelcard and the first visual indicator in a direction toward a location ofthe first plug-in port relative to the main frame; receive firstinfusion information from the first medication delivery module via thefirst plug-in port; provide for display on the display of the mainframe, within the first graphical channel card, at least a portion ofthe received first infusion information; determine, after orientatingthe edge of the first graphical channel card, that a second medicationdelivery module was electronically coupled to the main frame via asecond plug-in port of the main frame on a side of the main frameopposite to the first plug-in port; receive a second infusioninformation from the second medication delivery module; and dynamicallyprovide a second graphical channel card for display on the displaydevice of the main frame, adjacent to the first graphical channel card,with a second visual indicator along an edge of the second graphicalchannel card oriented toward the second plug-in port and oriented in adirection opposite the edge of the first graphical channel card.
 12. Thesystem of claim 11, wherein the main frame comprises a memory circuit,and the one or more processors are further configured to execute theinstructions to store the first infusion information in the memorycircuit.
 13. The system of claim 11, wherein the one or more processorsare further configured to receive a user selection of the firstgraphical channel card, and to execute the instructions to dynamicallyexpand the first graphical channel card, from a first summary state to asecond detail state, to display a detailed portion of the first infusioninformation upon receipt of the user selection, and to expand orcontract the first graphical channel card based on a number of activechannels in the patient care unit.
 14. The system of claim 11, whereinthe one or more processors are configured to execute the instructions toprovide display information to a display of the first medicationdelivery module to facilitate the display at the first medicationdelivery module.
 15. The system of claim 11, wherein the one or moreprocessors further execute instructions to verify that the firstmedication delivery module is associated with a patient registered withthe patient care unit.
 16. The system of claim 11, wherein the mainframe comprises a communications module configured to communicate with acontroller remote from the main frame over an electronic network, andthe one or more processors further execute instructions to transmit tothe controller, via the communications module, the first infusioninformation.
 17. A non-transitory, computer-readable medium storinginstructions which, when executed by a processor in a computer, causethe computer to perform a method, the method comprising: receiving, in amain frame of a patient care unit, a first indication that a firstmedication delivery module was electronically coupled with the mainframe via a first plug-in port of the main frame; displaying, on adisplay of the main frame responsive to receiving the first indication,a first graphical channel card representative of the first medicationdelivery module and having a first visual indicator along an edge of thefirst graphical channel card, wherein the first visual indicator isconfigured to display information associated with a status of the firstmedication delivery module; dynamically orienting, responsive toreceiving the first indication, the edge of the first graphical channelcard and the first visual indicator in a direction toward a location ofthe first plug-in port of the main frame; receiving infusion informationfrom the first medication delivery module via the first plug-in port;displaying, on the display of the main frame, within the first graphicalchannel card, at least a portion of the received infusion information;and expanding the first graphical channel card, from a first summarystate to a second detail state, to display a detailed portion of theinfusion information upon receipt of a user selection.
 18. Thenon-transitory, computer readable medium of claim 17, wherein in themethod, displaying the first graphical channel card in the main framecomprises mirroring a display in the first medication delivery module.19. The non-transitory, computer readable medium of claim 17, the methodfurther comprising: receiving a second indication that the firstmedication delivery module was electronically decoupled from the firstplug-in port and then electronically coupled to the main frame via asecond plug-in port associated with the main frame on a side of the mainframe opposite the first plug-in port; and dynamically reorienting theedge of the first graphical channel card and the first visual indicatortoward the second plug-in port.
 20. The non-transitory, computerreadable medium of claim 17, the method further comprising: receiving asecond indication that a second medication delivery module waselectronically coupled to the main frame via a second plug-in port ofthe main frame at a side of the main frame opposite the first plug-inport and the first medication delivery module; and dynamicallydisplaying, with the first graphical channel card, on the display of themain frame in response to receiving the second indication, a secondgraphical channel card oriented in a direction toward the second plug-inport and such that an edge of the second graphical channel card isoriented in a direction opposite the edge of the first graphical channelcard, the second graphical channel card including at least a portion ofa second infusion information.